5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
- Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-4: Understanding Process Design

The Sequence of Operation


The components of a process operate in a defined sequence so that there is a consistent pattern of operation, no matter what type of process is defined. For example, if a process has several frames that include optional and automatic children, and many of the frames also contain images, you need to understand APPX's processing sequence to achieve your intended design objective.

The primary control mechanism within a process is a frame. If a process has more than one frame, they operate in sequence based on a number you assign. APPX executes one complete process cycle (all frames one after the other) for each selected record in a process control file. For input processes, users select the records. For update and output processes, records may be selected by a previous query process; otherwise, the entire file is used. Thus, for an update or output process, if there are 100 selected records from the PCF, the entire frame cycle will execute 100 times.

A frame may include an image (or several alternate images), and invoke one or more automatic children, as well. APPX executes all the components of one frame before proceeding to the next.

Child processing is controlled in two fundamentally different ways. An optional child is always invoked by a user selecting an option key, and is always invoked from an image. An automatic child is invoked at the appropriate time without user intervention. For example, as soon as a user finishes entering data for an order in an order entry input process, a line item input process may automatically be invoked when the user selects Enter .

Because of the basic difference between optional and automatic children as described above, there is not a conflict with the order of invocation. Because a child is also a process, it can include a number of its own components. The same rules regarding order of invocation as described previously also apply for a process that is itself a child. You can therefore design a process that has various levels for which the sequence of operation is always predictable.

Application Design Manual                                         "Powered by Appx Software"

77

©2006 By APPX Software, Inc. All Rights Reserved